BlueOnyx 5211R/5210R: YUM and ISO updates

The new features from BlueOnyx 5212R have been ported back to BlueOnyx 5211R and 5210R.

After yesterdays release of BlueOnyx 5212R we have now ported back the following improvements to BlueOnyx 5211R and 5210R and published them as YUM updates.

Updated ISO images and Incus/LXC images have also been released.

base-alpine:

• The network traffic graphs now render correct traffic deltas.
• i18n: Localization of empty tags returns early.

base-apache:

• Vsite Template now has PHP enabled by default, allowing to directly choose the PHP version during Vsite creation.
• Overhauled 'badbot' mechanism for Apache.
• New mechanism for treating web access to suspended Vsites by directing all traffic to new suspension page.

base-vsite:

• Modernized index.html and error pages for new Vsites.
• Added /usr/sausalito/sbin/update_vsite_templates.pl to covert old index.html and error pages of Vsites to the new format.
• Added mechanism that Easy-Migrate can use to perform index.html and error pages conversion on migrations.
• Vsite deletion now resets over-quota status of Users and Vsite to make sure the MTA over-quota entries of that Vsite are removed.
• Modified /usr/sausalito/configs/php/set_php_headers.php to add over-quota info text headers and footers to Vsites that are over-quota.
• Switch to suspend a Vsite got extended and now allows to add an optional text or html message that is show during web access attempts to a suspended Vsite.
• Vsite Add now asks for name, username and password of a siteAdmin that is created along with the Vsite. This siteAdmin then becomes owner of the Vsite's /web directory.
• In case of errors during Vsite creation most (but not all) input values are now retained.

base-am:

• Minor bugfixes for CPU and Memory charts show in Active Monitor.

base-disk:

• Disk Usage display in Active Monitor got several retouches regarding display of maximum allowed disk quota for users.

base-email:

• MTA is now restarted on suspend/unsuspend over users.
• Improved over-quota handling for Users and Vsites.
• Better cleanup of over-quota states if users are again within their quota limits.
• Overhauled the Sendmail config importer of Postfix and removed several deprecated flags from the Postfix configuration.

base-mysql (5211R only):

• Improved handler for MariaDB password changes. This now also removes the socket authentication from user root@localhost as that caused more grief than it was worth.
• Changes of password for MariaDB user "root" now changes the password of all MariaDB "root" users.
• If MariaDB user root@127.0.0.1 doesn't exist he will be created.
• Simplified logic in MariaDB related UI extensions.

base-network (5211R only):

• The mechanism to determine the primary network interface got improved.
• Improved rendering of network traffic via Flot chart.
• Improvements in "System Settings" / "TCP/IP" to be able to more reliably detect and configure the network interfaces.
• Added a provision to NetworkManager that makes sure that it is restarted automatically in case it dies for whatever reason.
• Revised which network interface names are valid and improved support for various atypical network interfaces that might be encountered.

base-sitestats:

• Minor permission fix.

base-swupdate:

• Disabled caching of "ActiveMonitor" object on the page that configures the NewLinQ settings.
• If a BlueOnyx is already linked to NewLinQ, the menu "Install PKGs" will now redirect to "Third Party Software" to avoid confusion.

base-user:

• The GUI page that handles user deletion will now reset any present over-quota state of a user before it performs the deletion to clear up potential MTA entries of that user to that end.

CMU:

• Updated with provisions to migrate to and from BlueOnyx 5212R

Easy-Migrate:

• Updated with provisions to migrate to and from BlueOnyx 5212R

Swatch:

• Updated with provisions to attempt a one-time conversion of Vsite index.html and error pages to the new styles.

What this achieves:

With these set of YUM update BlueOnyx 5211R is almost on par with our latest BlueOnyx 5212. The only real difference between 5212R and 5211R are OS related. BlueOnyx 5212R of course has the more modern OS, newer libraries and a longer lease of life. But for all practical purposes a BlueOnyx 5211R is still "good enough" and provides the same features as far as typical usage goes.

As for BlueOnyx 5210R? While it now has most of the new features and fixes of its younger siblings? It's growing a beard and is getting long in the tooth due to its age. It still has life left in it, but there are parts in BlueOnyx 5210R that we can't bring forward due to legacy reasons. Such as the network handling (which still has OpenVZ 7 provisions, too!) and a few select other aspects where moving forward would cause rifts and rock the boat unnecessarily. But for the most part? We managed to port back what could be ported back.

Problems and issues?

Speaking about "rocking the boat": Large updates like this (about 100 RPMs in one go) always have a chance that something doesn't work out as intended. That some bugs were introduced during porting and haven't found in testing. If you encounter any issues after the YUM update of your BlueOnyx 5210R or 5211R, then please let us know. Either by filing a Support Ticket through the GUI of your BlueOnyx, via email, the mailing list or on our Discord server.